simensen
Repos
179
Followers
287
Following
5

Events

Is it possible to schedule something every 14 days, and if so, is it possible to specify "starting from this day"?

It seems like many cron expressions are specific to the implementation and it isn't clear to me if any of these things are possible with this specific library.

My end goal is wanting to create a cron expression that runs at 10:30am every 14 days (fortnightly), starting with Tuesday, September 13th. The human-readable form would be, "every other tuesday at 10:30am" but the "every other" should be based on a specific tuesday being the seed.

I feel like I've seen some implementations that let you specify "starting at", but I'm not sure if it was cron or something more like caldav for recurring events. :)

I figured the easiest thing (for me) to do would be to ask her if this is even remotely possible with this library before trying to hack a solution only to find out "nope, this wasn't ever going to be doable."

Thanks. :)

Created at 3 weeks ago
issue comment
Add the ability to see and copy JSON snippet

I think I'll leave this one for now. :) I don't have enough time to figure out how to do this and I already have a workaround. Thanks for merging #44. That is the main thing that will make my life easier. :)

Created at 1 month ago
delete branch
simensen delete branch no-minimum
Created at 1 month ago
pull request opened
Allow for steps as small as 0% for stepping up and stepping down

This was the simple fix for this. My local testing seems to imply this works great. I didn't see a way to test things beyond firing up serve and seeing the UI visuals updated to the new range starting at 0% instead of 3%. I also tested opening a color that was saved with less than 3% and it showed up as expected.

Closes #42

Created at 1 month ago
create branch
simensen create branch no-minimum
Created at 1 month ago
Created at 1 month ago
Add the ability to see and copy JSON snippet

I'd be interested in having the ability to see and copy the color information as a JSON-compatible snippet in addition to the existing JavaScript snippet.

My use case is for tooling around colors that involve reading and consuming something like colors.json in some parts of the application but could also be used to inject as parsed JSON into tailwind.config.js.

Right now I'm doing this in my tailwind.config.js:

const colors = require('../branding/colors.js')

const fs = require('fs');

fs.writeFileSync('../branding/colors.json', JSON.stringify(colors));

module.exports = {
  theme: {
    extend: {
      colors,
    },
  },
}

Which is fine, but it would be nicer if I could maintain colors.json instead of colors.js and not have an extra build step required to get colors.json to exist.

const colors = require('../branding/colors.json')

module.exports = {
  theme: {
    extend: {
      colors,
    },
  },
}

Is this something you'd consider adding or supporting if I sent a PR?

Created at 1 month ago
What are the reasons 3% is the min/max for steps?

I have several colors for which the color bottoms out at pure black or tops out at pure white by or before -50 or -900. In some cases, I've been able to tweak the colors manually by setting the step up or step down values to 2% or 1%. This works great! Unfortunately, when I save these colors in this state, loading them again overrides the values I manually set to 2% or 1%. This makes it look like the color was never saved and resets the step values to 1%. Since these values are different than the color I actually saved (with 2% or 1% values) it gives me the option to "save" the color again.

An example that goes to white:

https://www.tailwindshades.com/#color=180%2C37.77777777777776%2C91.17647058823529&step-up=3&step-down=3&hue-shift=0&name=aqua-squeeze&base-stop=5&overrides=e30%3D

This screenshot shows what I can see while this link is open:

image

This screenshot shows what happens when I manually type "1" into the step up field:

image

I know the UI says it only allows 3%-20%, so one could argue the fact that I can temporarily trick it at all is probably the bug. :) That said, I'm curious what reasons there are for limiting the stepping to 3% at most and whether you'd consider relaxing this restriction.

I think I found the bit of the code that normalizes this value to bottom at 3% and would be happy to send a PR adjusting this to 1%.

https://github.com/leoquack/tailwindshades/blob/8528bb43e4140ae3d6ac35d3589a4172d968ee00/src/components/Shades.vue#L593-L612

I'd probably also include a change to the UI to update to the 1% minimum to match the normalization on the back end.


Are you interested in a PR relaxing the 3% minimum? If so, are there other things you feel I should keep in mind?

Thanks for this tool. :)

Created at 1 month ago

Added Dash

Created at 2 months ago

atom

Created at 2 months ago

Add etcher and Google Drive

Created at 2 months ago