Releases: edge-js/edge
Adding hooks for claiming and modifying tags
Adding support for defining pre-processor to be executed on every line
- feat: add support to hook into raw line processing 75d344c
Add @share tag and improvements to `$props` and `$slots` api
- refactor: remove unused imports bb7d1cd
- refactor: remove raise method from caller and add to globals b24b699
- feat: add @share tag to share values from component to caller 63ca0ba
- feat: add dedicated classes for Props & Slots for easier interaction 16fd508
- feat: expose api to register plugins e228e0f
- chore: update dependencies d7de3d8
Updating lexer and parser as they contain bug fixes
- chore: update dependencies 2787f37
Add supporting for defining template pre-processors
Update underlying dependencies
Update dependencies
- chore(package): update dependencies 29b5e92
Improving the way new lines are handled
This release contains changes to the way new lines are handled and enhances the tags syntax to allow striping new line after the openining block of a tag.
Since Edge is extensively used for generating HTML, we do not expect any breaking changes after this change, since HTML is no meaning for new lines \n.
However, if you face any issues in your existing apps, then feel free to get in touch with me
Commits
Fix for release v3.0.4
- fix: ensure indexOf is greater than -1 43c0dd3
Depreciating dot based template paths
Before this release
Earlier one was able to use dot (.) as a separator to define nested template paths. For example:
// file path: posts/index.edge
view.render('posts.index') However, allowing dot as a separator can cause unnecessary problems, when the actual filename has a dot inside it. For example:
├── partials
│ └── header.small.edgeNow, rendering the view using partials.header.small will break, since the dot is used a path separator.
After this release
Now, the standard / is used for referencing nested paths.
view.render('posts/index')- refactor: depreciate dot based template paths 7bd3640