Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade d3 #11090

Closed
wants to merge 16 commits into from
Closed

Upgrade d3 #11090

wants to merge 16 commits into from

Conversation

timkelty
Copy link
Contributor

@timkelty timkelty commented May 4, 2022

@brianjhanson Assigning this to you, just because you're closer to it at the moment, but happy to take it back, or go through it together.

timkelty and others added 11 commits April 7, 2022 08:52
# Conflicts:
#	package-lock.json
#	src/web/assets/admintable/dist/css/app.css
#	src/web/assets/admintable/dist/js/app.js
#	src/web/assets/admintable/dist/js/app.js.LICENSE.txt
#	src/web/assets/admintable/dist/js/app.js.map
#	src/web/assets/cp/dist/cp.js
#	src/web/assets/cp/dist/cp.js.map
#	src/web/assets/cp/src/js/Chart.js
#	src/web/assets/d3/webpack.config.js
#	src/web/assets/pluginstore/dist/css/app.css
#	src/web/assets/pluginstore/dist/css/app.css.map
#	src/web/assets/tailwindreset/dist/css/tailwind_reset.css.map
@steverowling
Copy link
Contributor

Is there a chance that this will get accepted and a more recent version of d3 will be included with Craft? I have a plugin idea that requires d3 ^6.6.1, which conflicts with the current version that ships with Craft (4.13.0). To get it to work, I have to render on a page outside of the Craft CP, whereas I would love to be able to get it to work in a CP page. Alternatively, is there a way of forcing a newer version of d3 to load on a specific CP page?

@brandonkelly brandonkelly changed the base branch from develop to 5.0 August 17, 2022 20:43
@brandonkelly
Copy link
Member

@steverowling It would be a breaking change so will happen for Craft 5 instead.

# Conflicts:
#	package-lock.json
#	src/web/assets/admintable/dist/js/app.js.map
#	src/web/assets/cp/dist/cp.js
#	src/web/assets/cp/dist/cp.js.map
#	src/web/assets/d3/dist/d3-format/locale/ru-RU.json
#	src/web/assets/garnish/dist/garnish.js.map
#	src/web/assets/graphiql/dist/graphiql.js
#	src/web/assets/graphiql/dist/graphiql.js.map
#	src/web/assets/pluginstore/dist/js/app.js.map
#	src/web/assets/upgrade/dist/UpgradeUtility.js.map
@brandonkelly
Copy link
Member

@timkelty May be the fault of my merge commit but I’m getting d3 is not defined JS errors on this branch.

@timkelty
Copy link
Contributor Author

timkelty commented Sep 8, 2022

@brandonkelly not seeing any errors in my console 🤔

FWIW - d3 shouldn't be defined (globally at least) since we're just including as a proper module in this branch.

@timkelty timkelty assigned brianjhanson and timkelty and unassigned timkelty Jan 12, 2024
timkelty and others added 3 commits January 12, 2024 00:27
# Conflicts:
#	package-lock.json
#	src/web/assets/admintable/dist/js/app.js
#	src/web/assets/admintable/dist/js/app.js.map
#	src/web/assets/cp/dist/cp.js
#	src/web/assets/cp/dist/cp.js.map
#	src/web/assets/dashboard/dist/Dashboard.js.map
#	src/web/assets/garnish/dist/garnish.js.map
#	src/web/assets/graphiql/dist/graphiql.js
#	src/web/assets/graphiql/dist/graphiql.js.map
#	src/web/assets/htmx/dist/htmx.min.js
#	src/web/assets/pluginstore/dist/css/app.css
#	src/web/assets/pluginstore/dist/css/app.css.map
#	src/web/assets/pluginstore/dist/js/app.js
#	src/web/assets/pluginstore/dist/js/app.js.LICENSE.txt
#	src/web/assets/pluginstore/dist/js/app.js.map
#	src/web/assets/tailwindreset/dist/css/tailwind_reset.css
#	src/web/assets/upgrade/dist/UpgradeUtility.js.map
#	src/web/assets/vue/dist/vue.js
#	src/web/assets/vue/dist/vue.js.LICENSE.txt
@timkelty
Copy link
Contributor Author

Closed in favor of #14124

@timkelty timkelty closed this Jan 12, 2024
@brandonkelly brandonkelly deleted the upgrade-d3 branch January 12, 2024 17:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants