luckyframework / lucky Goto Github PK

The Lucky philosophy is to try to be at the intersection of happiness, usefulness, ease of use, what you can get paid for, and what is fulfilling. A framework with as few tradeoffs as possible.

I want to make it easy for beginners to figure out the types of things. This will be helpful when using assigns in Pages, or really for anytime you need a type

macro show_typeof(var)
  raise "Type of `{{var.id}}` is: #{typeof({{var}})}"
end

number = 1
show_typeof(number)

If you have the same assign in multiple pages it duplicates it the asking. That needs to be fixed

Some proof of concept code: https://gist.github.com/paulcsmith/b26cfcaf82c4ff87e9dcc46f6c42e48b

Sometimes macro finished doesn't work as expected when you use a server. Test this out to make sure things work correctly

https://github.com/luckyframework/web/blob/master/src/lucky_web/html_view.cr#L25

Maybe using methods on the type https://crystal-lang.org/api/0.22.0/Crystal/Macros/TypeNode.html#ancestors%3ACrystal%3A%3AMacros%3A%3AArrayLiteral%28TypeNode%29-instance-method

Make it clear what's coming from assigns, also less likely to have collisions with existing methods this way

I really like the one here: https://github.com/wp-cli/wp-cli#support

For request specs

Something I've actually used (also includes FactoryBot like factories):
https://gist.github.com/paulcsmith/c5da6e8888d1a50f13fb6d9acc37a6a9

Some experimental ideas:
https://gist.github.com/paulcsmith/d44ac002bd1b7c57dcb8f7217ac499a7

Pages don't need much to get started

html = MyCoolPage.new(whatever_args).render

html.to_s.should contain("some text")

class InnerPage < BaseView
  layout BaseLayout # This would probably go in the BaseView

  def inner
    # The inner page
  end

  def title
    "A great title"
  end
end

class BaseLayout < BaseLayout
  @page : BaseView

  def render
    title @page.title
    main do
      # Consider forwarding missing to @page so you can use it's helpers more easily
      @page.inner
    end
  end
end

Instead of this old way

class InnerPage < LuckyWeb::HTMLView
  def render
    Layout.new(self).render.to_s
  end

  def title
    "A great title"
  end
end

class Layout < LuckyWeb::HTMLView
  @page : InnerPage

  def initialize(@page)
    @io = IO::Memory.new
  end

  def render
    title @page.title
  end
end

watches files and restarts server

https://github.com/webpack-contrib/file-loader#filename-templates

Possibly use https://github.com/kostya/modest and make some nice matchers

session.should have_content "My App", css: ".main-header"

Be honest. Help people make good technical decisions

https://blog.bradfieldcs.com/you-are-not-google-84912cf44afb

https://www.agwa.name/projects/git-crypt/ Transparent file encryption. Can use symmetric keys so devs can easily share it, or use GPG.

Add some lucky tasks to get it working well, make it easy to publish the key to Heroku on setup

lucky secrets.encrypt_file # Add file(s) to .git-attributes
lucky secrets.sync_key prod # Pushes the key as an env var on Heroku

• http://www.twinbit.it/en/blog/storing-sensitive-data-git-repository-using-git-crypt
• https://news.ycombinator.com/item?id=7508734

So it can be inherited from in the default lucky deploy task, but can be overridden if you want to implement your own task

render user: UserRows.first

Remember to use hidden field so we get the unchecked value. This will work similar to the text_input helpers https://github.com/luckyframework/web/blob/master/src/lucky_web/tags/input_helpers.cr

http://stackoverflow.com/questions/11550941/why-does-the-check-box-form-helper-generate-two-checkboxes-one-hidden

Also: https://github.com/plataformatec/simple_form/blob/master/lib/simple_form/inputs/boolean_input.rb#L93

macro memoize(type_decl)
  @{{type_decl.var}} : {{type_decl.type}}?
  def {{type_decl.var}}
    @{{type_decl.var}} ||= {{yield}}
  end
end

class Users::Index < BaseAction
  memoize users : UserQuery do
    UserQuery.all.active
  end
end

https://play.crystal-lang.org/#/r/25hp
Also an interesting version here https://play.crystal-lang.org/#/r/25ha

data_confirm -> data-confirm

class Users::IndexPage < MainLayout
  needs users : UserQuery

  render_template # Assumes ./index_template.ecr/.slang - Use kilt to support just about anything
  
  # or specify template
  render_template "./some_other_extension.rss.ecr
end

The default would still be to use the HTML tag methods, but sometimes it's much nicer to use templating languages like ECR when doing content heavy pages like landing pages, pricing pages, etc. They're usually quite simple and have large paragraphs of text, which work better in template languages

https://kev.inburke.com/kevin/things-to-use-instead-of-jwt/

Or maybe the raw helper is already enough?