v5.0.0
#2332
Replies: 1 comment
-
Hey everyone (& @MarkBind/active-devs) I just wanted to send a quick message to express my heartfelt thanks to all of you for your incredible contributions that made our latest release possible. Lots of work culminated in this huge release!!! 🚀 🚀 For any discussions on migration issues, please comment below. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
markbind-cli
User Facing Changes
Breaking Changes
1. Change scroll top button to component by @yucheng11122017 in #2170
Scroll to Top button is changed to a component to allow for more flexibility in its usage. This includes allowing users to
It is no longer automatically added to pages on the website. To add the Scroll to Top Button to a website, add the component to the layout page
This button is still added to the default layout when users initialise a MarkBind project.
2. Update
deploy
command to build site before deployment by @lhw-1 in #2218The
markbind deploy
command now builds and generates the site by default, and this automatic build step can be skipped using the newly introduced--no-build
flag. This change is to accommodate the common use case consisting of the following steps:The
markbind build
step can now be omitted.It should be noted that if you have been generating your site with specified values for
baseUrl
or path tositeConfig.json
, you should add the--no-build
flag to themarkbind deploy
command to avoid re-building the site with default values.3. Deprecate slots, attributes and syntax by @itsyme in #2208
Currently, there are quite a few attributes/slots/syntaxes that are deprecated. They may or may not be listed in the docs, implemented in the codebase, or log a warning when used. We now completely remove them.
Overview:
modal-footer
->footer
modal-header
->header
has-input
->type="text"
{{ prefix_name }}
->:prefix_name:
[1] This seems a bit more complex compared to the others - it looks like there is some backwards compatibility intentionally preserved (#1274, #1293)
To migrate:
Modal:
modal-header
->header
modal-header
attribute has been fully deprecatedmodal-header
attribute with justheader
with the text in the attribute unchanged<modal modal-header="HEADER TEXT">
to<modal header="HEADER TEXT">
modal-footer
->footer
modal-footer
attribute has been fully deprecatedmodal-footer
attribute with justfooter
with the text in the attribute unchanged<modal modal-footer="FOOTER TEXT">
to<modal footer="FOOTER TEXT">
Question:
has-input
->type="text"
has-input
attribute has been fully deprecatedhas-input
attribute withtype="text"
<question has-input>
to<question type="text">
type
attribute) now not supportedmcq
,checkbox
,blanks
,text
Icons:
{{ }}
->: :
{{
and}}
to:
{{emoji-name}}
to:emoji-name:
4. Deprecate theme attribute in site config JSON by @itsyme in #2235
Fully deprecates
theme
attribute in site config JSON.theme
attribute in site config JSON has been fully deprecated.To migrate:
Use
"style": {"bootstrapTheme": "..."}
instead of"theme": "..."
.For example,
Original (in site.json):
Updated (in site.json):
5. Upgrade to use node 16 by @yucheng11122017 in #2233
Node.js version 14 is no longer supported by Markbind as it is due to reach it's end of life in 30 April 2023. The minimum required version of Node.js is now 16. Users are to upgrade to at least version 16 of Node.js.
6. Upgrade PlantUML version to 1.2023.10 by @lesterong in #2311
The PlantUML plugin has been updated from 1.2020.7 to 1.2023.10.
Changes
(For detailed changes, please view them on plantuml website)
skin rose
directive.set separator none
command.<u>Class Name</u>
will render an underline, but not__Class Name__
.7. Clean up docs & tests for variables by @tlylt in #2301
A newly generated site (e.g. via
markbind init
) will no longer contain the following erroneous line in_markbind/variables.md
:This way of importing variables from an external file within the global variables.md is not supported.
For existing sites migrating to the latest version, please check that you do not have the above line in your
_markbind/variables.md
file as it will not work as expected and will log a warning. Please remove such a line if found.8. Replace jQuery with vanilla JS by @yucheng11122017 in #2130
jQuery is no longer supported in Markbind. This is because jQuery is no longer as relevant since it can be replaced with modern DOM APIs.
If jQuery is used in your website, either
9. Generate .gitignore on init command by @lhw-1 in #2248
A
.gitignore
file is now added by themarkbind init
command by default.This file is only generated when initializing a new MarkBind site from scratch, and not when converting a set of pre-existing documents into a MarkBind site using
markbind init --convert
. As such, this does not require any additional actions from the user.10.Upgrade fontawesome version to latest (v6) from v5 Resolves #2242 by @SPWwj in #2326
We upgraded from fontawesome-free@5.15.4 to fontawesome-free@6.4.0.
The current icons will be preserved (i.e. you don't have to make any changes if you don't want to) due to Font Awesome's backward compatibility.
With Version 6
For details please refer to Font Awesome's changelog
Features
Enhancements
Fixes
Documentation
Developer Facing Changes
Code Quality
title
tags in generated tests by @lhw-1 in Remove emptytitle
tags in generated tests #2186DevOps Changes
Dependencies
Miscellaneous
(We reverted the implementation below due to further discussion required)
Full Changelog: v4.1.0...v5.0.0
This discussion was created from the release v5.0.0.
Beta Was this translation helpful? Give feedback.
All reactions