Added left/center/right alignment

[calumk]

Added left/center/right justify block settings.

Attempted to mirror the style of your previous code for legibility.
uses align as the parameter, defaults to left

{
  type: 'alert',
  data: {
    type: 'danger',
    align: 'center',
    message:
      '<strong>Holy smokes!</strong><br/>Something seriously <em>bad</em> happened.',
  },
}

I used align icons from https://github.com/codex-team/icons
I opted to import svg's directly instead of importing the @codex-team/icons package, as you were already using svg in the asset folder - But this could be simplified in the future by adding @codex-team/icons as a dependancy

[vishaltelangre]

Suggested change

	import IconAlignLeft from '../assets/IconAlignLeft.svg';
	import IconAlignCenter from '../assets/IconAlignCenter.svg';
	import IconAlignRight from '../assets/IconAlignRight.svg';
	import AlignLeftIcon from '../assets/align-left-icon.svg';
	import AlignCenterIcon from '../assets/align-center-icon.svg';
	import AlignRightIcon from '../assets/align-right-icon.svg';

Not a big deal, but it would help preserve the existing naming convention style.

[calumk]

If i commit here, without changing the file names themselves, i assume that will break things - not sure on the best way to resolve, commit then pull the repo then push a new change with filename changes and the code changes?

[vishaltelangre]

Pull using git pull origin master, commit changes and then push it. Everything happens on your fork. Once the PR is merged, all the changes in your fork's master would then be merged to the master branch of this repo.

[vishaltelangre]

Not quite sure why this manifest is changed. Any idea (because we are not touching package.json at all in this PR)?

[calumk]

I accidently used npm i / npm build instead of yarn while i was developing, possible i caused some issue here?

[vishaltelangre]

Yeah, that's what seemed to have caused it. Can you please revert it?

[vishaltelangre]

@calumk Left some nits, but looks good otherwise!

[calumk]

@vishaltelangre updated notes

Sorry, this is one of the first times im commiting a PR requiring modification to somebody elses repo, so unsure on how to proceed on the icons issue

Do i make a new commit to my fork, and then open a new PR to resolve that? - what is the best way forward?

[vishaltelangre]

It appears that if you update your fork's master branch, it would automatically reflect in this PR.

[calumk]

I think I have now rolled back the yarn.lock - in the end i copied and pasted the whole file, because running yarn installseems to updates yarn.lock to newer versions

[vishaltelangre]

Thanks. 🙏 I will merge and publish a new version to npm registry tomorrow.