Features v0.12 #783
Merged
Features v0.12 #783
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add tags dropbar menu - Use ReactionUI tags for interface - Sortable nested tags - Added es7 features with .babelrc - Enabled ReactionUI package for reaction and reaction-core
# Conflicts: # packages/reaction-core/client/templates/layout/header/tags/tags.js
# Conflicts: # .meteor/versions
You can now validate a Tag, and an array of Tags for react components
Moved tag navigation to its own package. Removed tag navigation from core. Tags now only go 3 deep in the UI, but now show up as a tree for easier navigation.
Tag nav dropdown now shows on hover, and lock open while editing. Cleanup of code
To keep consistent with the rest or reaction, moving the tagnav back to blaze.
Added ability to move tags between groups. Added ability to move tags between main navigation and groups Added ability to sort groups
- Added toggle for edit state - Added hover for dropdown in non editing modes - Added hrefs for tag links - Code cleanup
Wrap edit task button in conditional Update style
- Added remove - Added update
- so that we don’t need to check if dashboard icon is different than others..
- WIP dashboard grid
index should be used for shop home
Add product button in sidebar is now shows a popover with all shortcuts from register with container=addItem. This includes the add product shortcut.
- all routes are defined in registry now, with the exception of paypal
- use registry.name instead of registry.route for routing - routes will still work in permissions checks - remove unnecessary template hasPermission checks - updated shop members ui to work with names (WIP) - changes dashboard header i18n to match format introduced for admin labels. adds `labelTitle`
# Conflicts: # packages/reaction-layout/client/templates/layout/admin/admin.html
TODO - add i18n to this and use labels.
should be ok without, publications now using Roles.userInRoles.
|
@ramusus there's a couple broken tests still, but the hasPermissions should be ok now (removed checks). |
This was referenced Feb 17, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Release Notes v0.12
There are breaking changes with this release, it is recommended to start with a
resetas existing data may not be compatible, but the key collection changes are forShopsandPackages.There are 155 passing server integration tests for this release.
Changes
reaction-routerpackage.Routerdeprecated, useReactionRouterrenderLayoutTagsnavigation and management.reaction-uipackage.CoreDashboard settings.icon-reaction-logofontAlertsmethodstoastandinlineandalert.pathForSeoandcurrentRouteare deprecated, usepathFor.i18ndeprecated, usei18next.i18nextupdated to v2.0reactionApps,reactionTemplates, use:{{i18n i18nKeyLabel label}}package.registry.nameas the key (not route).Productscollections now use a flattened, multi-schema implementation.Contributions
A sincere thanks from the core team of @aaronjudd, @mikemurray, @jshimko, @zenweasel, @saralouhicks for all the community contributions we accepted into this release. We merged requests from @newsiberian, @lijiming, @hrath2015, @spencern, @ramusus, @meladawy, @johannes-scharlach, @tdecaluwe, @uniquarkD